-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Chassis][Voq]Update sonic-buffer-queue and sonic-queue for Voq Chassis #18875
[Chassis][Voq]Update sonic-buffer-queue and sonic-queue for Voq Chassis #18875
Conversation
It seems that you want to add two new tables, would you please update same_config_db.json and cofiguration.md? |
|
||
key "hostname asic_name port qindex"; | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick: remove extra space
(/sdm:sonic-device_metadata/sdm:DEVICE_METADATA/sdm:localhost/sdm:switch_type='voq')"; | ||
key "hostname asic_name ifname qindex"; | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick: remove extra line
Besides the minor nitpicks, the changes look good to me. |
…is (sonic-net#18875) Why I did it The configuration for QUEUE and BUFFER_QUEUE differs between a VOQ device and a Non-VOQ devices. For the Voq device: The queue and buffer queue is applied on the system port. The system port is a representation of every port in a chassis, the key for systemport consists of Linecard Name , Asic Name and portname On a Non voq device: the queue and buffer queue configuration is applied on the front panel port. Due to this differences the yang models sonic-queue.yang and sonic-buffer-queue.yang does not work for Voq devices This is address in this PR Microsoft ADO (27252773 and 27252696): How I did it Update the yang model to have different CONFIG_LIST with different keys based on the following condition when the switch_type is not present or switch_type is not voq, the yang LIST will have key of port and queue_index when the switch_type is present and switch_type is voqhe yang LIST will have key of Linecard name, asi name, port and queue_index How to verify it UT and incremental config push on chassis
Why I did it
The configuration for
QUEUE
andBUFFER_QUEUE
differs between aVOQ
device and aNon-VOQ
devices.For the
Voq
device:The queue and buffer queue is applied on the system port. The system port is a representation of every port in a chassis, the key for systemport consists of
Linecard Name
,Asic Name
andportname
On a Non voq device:
the queue and buffer queue configuration is applied on the front panel port.
Due to this differences the yang models
sonic-queue.yang
andsonic-buffer-queue.yang
does not work for Voq devicesThis is address in this PR
Work item tracking
How I did it
Update the yang model to have different CONFIG_LIST with different keys based on the following condition
voq
, the yang LIST will have key of port and queue_indexvoq
he yang LIST will have key of Linecard name, asi name, port and queue_indexHow to verify it
UT and incremental config push on chassis
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)